-
Notifications
You must be signed in to change notification settings - Fork 989
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(analytics): Allow analytics to be configured per env #21975
base: develop
Are you sure you want to change the base?
Conversation
7d89cf6
to
61bf682
Compare
Jenkins BuildsClick to see older builds (18)
|
Thanks for the swift reviews guys! @siddarthkay I tagged you as a reviewer to help us configure the vars in Jenkins. The shadow-cljs code already allows passing the vars to the initialization code in status-go, so I believe it's just a matter of passing down the vars from Jenkins. The parent issue has the details about what we expect to be configured #21974 in Jenkins. When the time is appropriate for you, could you help us by adding the vars to Jenkins? Thanks! |
75% of end-end tests have passed
Not executed tests (2)Failed tests (2)Click to expandClass TestWalletOneDevice:
Class TestCommunityMultipleDeviceMerged:
Passed tests (6)Click to expandClass TestCommunityOneDeviceMerged:
Class TestWalletMultipleDevice:
Class TestWalletOneDevice:
Class TestOneToOneChatMultipleSharedDevicesNewUi:
|
@siddarthkay, please let me know when you have set up the CI with the vars |
61bf682
to
93040b8
Compare
Can get this done by tomorrow! |
4bf762e
to
72482b9
Compare
72482b9
to
b12d40a
Compare
Fixes #21974
Summary
Allows MixPanel to be configured per environment. The hardcoded MixPanel app ID and token are removed from the code (see the parent issue for more details). The token can be exploited and that's by design in analytics tools https://developer.mixpanel.com/reference/project-token, but we are being too kind at the same time, so I'm removing that from code ;)
Areas that may be impacted
Steps to test
I will test this PR myself.
Note: to test the correct values are set-up in Jenkins for release builds we need to generate a release build. That's the reason I committed a change to the
VERSION
file with the PR number, as I believe this is the recommendation from infra team.status: ready